System and method for encoding of local bandwidth conditions into tunneling message

ABSTRACT

A method, a system, and a non-transitory storage medium provide for encoding a general packet radio service (GPRS)-tunnel endpoint identifier (GTP-TEID) with data identifying radio frequency (RF) bandwidths supported in a local radio environment (LRE) from which a user equipment (UE) device accesses the wireless access station; sending, via a signaling channel, the GTP-TEID to a core network device; notifying one or more core network devices of an RF bandwidth category level corresponding to the identified RF bandwidths; and applying at least one of a policy rule or a charging rule to a packet data unit (PDU) session for the UE device, based on the RF bandwidth category level.

BACKGROUND

Radio access networks (RANs), in both standalone (SA) and non-standalone(NSA) architectures, may provide wireless services using a combinationof radio frequency (RF) bands. For example, different markets in ageographic region may use different combinations of RF bands based onthe amount of spectrum that is allocated for each RF band in aparticular market. In some scenarios, RF bands are combined in carrieraggregation and/or in a dual connectivity model to meet user equipment(UE) performance metrics such as accessibility, congestion, latency,throughput, etc. Various core network elements associated with a RAN maynot be informed of the RF bandwidths that support the RAN, for example,on a per bearer or a flow basis.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-B are diagrams illustrating an exemplary environment in whichan exemplary embodiment of the encoding of tunnel messaging system maybe implemented;

FIG. 2 is a diagram illustrating an exemplary process of an exemplaryembodiment of the encoding of tunnel messaging system;

FIG. 3 is a diagram illustrating exemplary components of a device thatmay correspond to one or more of the devices illustrated and describedherein;

FIG. 4 is a flow diagram illustrating an exemplary process of anexemplary embodiment of the encoding of tunnel messaging system; and

FIG. 5 is a messaging and operations diagram illustrating an exemplaryembodiment of the encoding of tunnel messaging system.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

A Fifth Generation (5G) new radio (NR) network may provide standaloneand non-standalone configurations. For example, for a non-standaloneconfiguration, a Long Term Evolution (LTE) Evolved Packet Core (EPC) maybe used, and for a standalone configuration, a 5G core (5GC) network maybe used. Additionally, for example, for non-standalone service, an LTEsub-6 cell (e.g., below 6 Gigahertz (GHz)) may be an anchor cell (e.g.,Master Cell Group (MCG)) that provides control signaling, and an NR bandmay be a secondary cell (e.g., Secondary Cell Group (SCG)) that provides(additional) data service. For standalone service, an NR band mayprovide control signaling and data service.

The RF bands that support a 5G network may vary to include certainranges, such as above 6 GHz and below 6 GHz, as well as other frequencyranges, such as sub-3 (e.g., below 3 GHz), mid-band (e.g., between 3 GHzand 6 GHz), low band, millimeter wave (mmWave), and so forth. Therespective RF propagation properties are such that a coverage providedby a lower RF band is larger than a coverage provided by a higher RFband. RF bands may also have significant discrepancies relative touplink (UL) and downlink (DL) coverage areas based on differences intransmit power and receiver capability (e.g., antenna array, noisefigure, etc.) between UE and RAN devices (e.g., evolved Node B (eNB),next generation Node B (gNB), etc.). Therefore, one local radioenvironment (LRE) within a RAN may be supported by a particularcombinations of RF bands while another LRE, near or distant to the firstLRE, but within the same RAN, may be supported by a differentcombination of RF bands.

Information regarding the RF bandwidths supported or available in anLRE, on a per bearer and flow basis, is not currently communicated fromthe RAN to the core network. As such, the appropriate quality of service(QoS), charging and traffic policies, etc., may not be employable by thecore network. For example, “low” bandwidth conditions in a local areamay not support providing high capacity 4 k content (e.g., videostreaming), whereas “high” bandwidth conditions may support providinghigh capacity 4 k content. Similar issues arise in a cell type orpresence reporting area information on a per bearer and flow basis. Asnetwork configurations evolve and available RF spectrum is added,challenges arise concerning optimal usage of the RF footprint and acorresponding service coverage. Implementations, as described herein,communicate bandwidth conditions at dedicated radio bearer (DRB) levelgranularity for use in policy control and charging scenarios.

FIG. 1A is a diagram illustrating a portion of exemplary environment 100in which an exemplary embodiment of the encoding of tunnel messagingsystem may be implemented. According to exemplary embodiments, anencoding of tunnel messaging system is provided that enables a RAN toinform a core network of local bandwidth possibilities and conditions.In one implementation, the local bandwidth possibilities and conditionsmay be communicated at the same time as RAN resources are allocated fora flow, for example, at the time of sending radio resource control (RRC)reconfiguration to a UE device 115. The encoding system may beimplemented using a general packet radio service (GPRS) tunnelingprotocol (GTP) user plane (GTPv1-U). According to an exemplaryembodiment, a logical uplink (UL) tunnel 102 between a wireless accessstation 110 (e.g., gNB, eNB, etc.) and a core network 150 (e.g., userplane function (UPF), packet gateway (PGW), etc.) may be identified by aGTP tunnel IP address 104, a GTP port number 106, and a GTP-tunnelendpoint identifier (TED) 108. According to an exemplary embodiment, alogical downlink (DL) 112 tunnel between wireless access station 110(e.g., gNB) and core network 150 may be identified by a GTP tunnel IPaddress 114, a GTP port number 116, and a GTP-TEID 118. The messagingsystem may include encoding GTP-TEID 118 with an extension identifyinglocal bandwidth possibilities and conditions at a flow or a DRB level.

According to an exemplary embodiment, once core network 150 receivesGTP-TEID 118 via a control plane signaling channel 103, a sessionmanagement function (SMF) device of the core network may analyze theencoded information and generate a presence reporting area (PRA) reportto other elements of the core network. For example, a policy function(PF) device and/or a charging function (CHF) device may select QoS, anetwork slice identifier (ID), charging, traffic management, datashaping, and/or other policies based on the local bandwidth conditionsand/or cell type identified in the PRA.

FIG. 1B is a diagram illustrating a portion of exemplary environment 100in which an exemplary embodiment of the encoding of tunnel messagingsystem may be implemented. As illustrated, environment 100 includes aradio access network (RAN) 105, and core network 150. RAN 105 includesaccess devices 110, and core network 150 includes core devices 155.Environment 100 further includes UE devices 115.

The number, type, and arrangement of networks illustrated in environment100 are exemplary. Additionally, or alternatively, other networks notillustrated in FIG. 1B may be included in environment 100, such as abackhaul network, a fronthaul network, an application layer network, oranother type of intermediary network.

The number, the type, and the arrangement of network devices in RAN 105,and core network 150, as illustrated and described, are exemplary. Thenumber of UE devices 115 is exemplary. A network device, a networkelement, or a network function (referred to herein simply as a networkdevice) may be implemented according to one or multiple networkarchitectures (e.g., a client device, a server device, a peer device, aproxy device, a cloud device, a virtualized function, and/or anothertype of network architecture (e.g., Software Defined Networking (SDN),virtual, logical, network slicing, etc.)). Additionally, a networkdevice may be implemented according to various computing architectures,such as centralized, distributed, cloud (e.g., elastic, public, private,etc.), edge, fog, and/or another type of computing architecture.

Environment 100 includes communication links between the networks,between network devices, and between UE device 115 and network devices.Environment 100 may be implemented to include wired, optical, and/orwireless communication links among the network devices and the networksillustrated. A communicative connection via a communication link may bedirect or indirect. For example, an indirect communicative connectionmay involve an intermediary device and/or an intermediary network notillustrated in FIG. 1B. A direct communicative connection may notinvolve an intermediary device and/or an intermediary network. Thenumber and the arrangement of communication links illustrated inenvironment 100 are exemplary.

Environment 100 may include various planes of communication including,for example, a control plane, a user plane, a service plane, and/or anetwork management plane. Environment 100 may include other types ofplanes of communication. A message communicated in support of theencoding of tunnel messaging system may use at least one of these planesof communication. According to various exemplary implementations, theinterface of the network device may be a service-based interface, areference point-based interface, an Open RAN (O-RAN) interface, or someother type of interface.

RAN 105 may include one or multiple networks of one or multiple typesand technologies. For example, RAN 105 may be implemented to include anext generation RAN (e.g., a Fifth Generation (5G)-access network(5G-AN) or a 5G-RAN (referred to herein as simply a 5G-RAN)), anothertype of future generation RAN, a Fourth Generation (4G) RAN (e.g., anEvolved UMTS Terrestrial Radio Access Network (E-UTRAN) of a Long TermEvolution (LTE) network), a 4.5G RAN (e.g., an E-UTRAN of anLTE-Advanced (LTE-A) network), an RAN of an LTE-A Pro network, and/oranother type of RAN (e.g., a legacy Third Generation (3G) RAN, etc.).RAN 105 may further include other types of wireless networks, such as aWi-Fi network, a Worldwide Interoperability for Microwave Access (WiMAX)network, a local area network (LAN), a Bluetooth network, a personalarea network (PAN), a Citizens Broadband Radio System (CBRS) network, oranother type of wireless network (e.g., a legacy Third Generation (3G)RAN, O-RAN Reference Architecture, a virtualized RAN (vRAN), aself-organizing network (SON), etc.). RAN 105 may include a wirednetwork, an optical network, or another type of network that may providecommunication with core network 150, for example.

RAN 105 may include different and multiple functional splitting, such asoptions 1, 2, 3, 4, 5, 6, 7, or 8 that relate to combinations of RAN 105and core network 150 including an EPC network and/or a NG core (NGC)network, or the splitting of the various layers (e.g., physical layer,Media Access Control (MAC) layer, Radio Link Control (RLC) layer, andPacket Data Convergence Protocol (PDCP) layer), plane splitting (e.g.,user plane, control plane, etc.), centralized unit (CU) and distributedunit (DU), interface splitting (e.g., F1-U, F1-C, E1, Xn-C, Xn-U, X2-C,Common Public Radio Interface (CPRI), etc.) as well as other types ofservices, such as dual connectivity (DC) or higher (e.g., a secondarycell group (SCG) split bearer service, a MCG split bearer, an SCG bearerservice, E-UTRA-NR (EN-DC), NR-E-UTRA-DC (NE-DC), NG RAN E-UTRA-NR DC(NGEN-DC), or another type of DC (e.g., multi-radio access technology(RAT) (MR-DC), single-RAT (SR-DC), etc.), carrier aggregation (CA)(e.g., intra-band, inter-band, contiguous, non-contiguous, etc.),network slicing, coordinated multipoint (CoMP), various duplex systems(e.g., frequency division duplex (FDD), time division duplex (TDD),half-duplex FDD (H-FDD), etc.), and/or another type of connectivityservice (e.g., NSA) (e.g., non-standalone NR, non-standalone E-UTRA,etc.), SA (e.g., standalone NR, standalone E-UTRA, etc.), etc.).

In an exemplary embodiment of the encoding of tunnel messaging system,environment 100 includes a split gNB that may include multiplegNB-distributed units (DUs) connected to a gNB-centralized unit (CU)connected to core network 150. For example, the gNB-DUs may supportmultiple different carriers and bandwidths. The gNB-CU and the gNB-DUsmay be connected using F1-U and NG-U interfaces. As an alternative to asplit gNB scenario, the system may be similarly applicable to an Option3x, split-eNB case (e.g., via a W1 interface), or alternatively, for aconnection to an evolved packet core (EPC)/5G core interworking.

Referring again to FIG. 1B, RAN 105 may be implemented to includevarious architectures of wireless service, such as, for example,macrocell, microcell, femtocell, picocell, metrocell, NR cell, LTE cell,non-cell, or another type of architecture. Additionally, according tovarious exemplary embodiments, RAN 105 may be implemented according tovarious wireless technologies (e.g., RATs, etc.), wireless standards,wireless frequencies/bands/carriers (e.g., centimeter (cm) wave,millimeter (mm) wave, below 6 GHz, above 6 GHz, licensed radio spectrum,unlicensed radio spectrum, NR low band, NR mid-band, NR high band,etc.), and/or other attributes of radio communication.

Depending on the implementation, RAN 105 may include one or multipletypes of network devices, such as access stations 110. For example,access stations 110 may include a next gNB, an eNB, an evolved Long TermEvolution (eLTE) eNB, a radio network controller (RNC), a remote radiohead (RRH), a baseband unit (BBU), a centralized unit (CU), adistributed unit (DU), a small cell node (e.g., a picocell device, afemtocell device, a microcell device, a home eNB, etc.), open networkdevices (e.g., O-RAN Centralized Unit (O-CU), O-RAN Distributed Unit(O-DU), O-RAN next generation Node B (O-gNB), O-RAN evolved Node B(O-eNB, etc.), a future generation wireless access device, another typeof wireless node (e.g., a WiMax device, a hotspot device, etc.) thatprovides a wireless access service. According to some exemplaryimplementations, access devices 110 may include a combined functionalityof multiple RATs (e.g., 4G and 5G functionality).

Core network 150 may include one or multiple networks of one or multipletypes and technologies. According to an exemplary embodiment, corenetwork 150 includes a complementary network of access network 105. Forexample, core network 150 may be implemented to include a 5GC network(also known as NGC network) (or other type of a future generationnetwork), an EPC of an LTE network, an LTE-Advanced (LTE-A) network,and/or an LTE-A Pro network. Core network 150 may include a legacy corenetwork.

Depending on the implementation, core network 150 may include varioustypes of network devices, such as core devices 155. For example, coredevices 155 may include a mobility management entity (MME), a packetgateway (PGW), an enhanced packet data gateway (ePDG), a serving gateway(SGW), a home agent (HA), a General Packet Radio Service (GPRS) supportnode (GGSN), a home subscriber server (HSS), an authentication,authorization, and accounting (AAA) server, a policy charging and rulesfunction (PCRF), a charging system (CS), a user plane function (UPF), aNon-3GPP Interworking Function (N3IWF), an access and mobilitymanagement function (AMF), a session management function (SMF), aunified data management (UDM) device, a unified data repository (UDR)device, an authentication server function (AUSF), a network sliceselection function (NSSF), a network repository function (NRF), a policycontrol function (PCF), a network data analytics function (NWDAF), anetwork exposure function (NEF), a lifecycle management (LCM) device,and/or an application function (AF). According to other exemplaryimplementations, core devices 155 may include additional, different,and/or fewer network devices than those described. For example, coredevices 155 may include a non-standard and/or a proprietary networkdevice, or another type of network device that may be well-known but notparticularly mentioned herein. Core devices 155 may also include anetwork device that provides a multi-RAT functionality (e.g., 4G and5G), such as an SMF with PGW control plane functionality (e.g.,SMF+PGW-C), a UPF with PGW user plane functionality (e.g., UPF+PGW-U), aservice capability exposure function (SCEF) with a NEF (SCEF+NEF),and/or other combined nodes (e.g., an HSS with a UDM and/or UDR, an MMEwith an AMF, etc.). Access network 105 and/or core network 150 mayinclude a public network, a private network, and/or an ad hoc network.

UE device 115 includes a device that has computational and wirelesscommunicative capabilities. Depending on the implementation, UE device115 may be a mobile device, a portable device, a stationary device, adevice operated by a user (e.g., UE, etc.), or a device not operated bya user (e.g., an Internet of Things (IoT) device, etc.). For example, UEdevice 115 may be implemented as a smartphone, a mobile phone, apersonal digital assistant, a tablet, a netbook, a phablet, a wearabledevice (e.g., a watch, glasses, etc.), a computer, a device in avehicle, a gaming device, a music device, an IoT device, or other typeof wireless device. UE device 115 may be configured to execute varioustypes of software (e.g., applications, programs, etc.). The number andthe types of software may vary among UE devices 115.

FIG. 2 illustrates an example environment 200, in which one or moreembodiments, described herein, may be implemented. Environment 200 maybe a 5G network, and/or may include elements of a 5G network. As shownin FIG. 2, environment 200 may include UE device 115, RAN 105, an AMF215, an SMF 220, a policy control function (PCF) 225, an applicationfunction (AF) 230, a UPF 235, a data network (DN) 240, a CHF 245, and aUDM 350.

The number of devices and/or networks, illustrated in FIG. 2, isprovided for explanatory purposes only. In practice, environment 200 mayinclude additional devices and/or networks; fewer devices and/ornetworks; different devices and/or networks; or differently arrangeddevices and/or networks than illustrated in FIG. 2. For example, whilenot shown, environment 200 may include devices that facilitate or enablecommunication between various components shown in environment 200, suchas routers, modems, gateways, switches, hubs, etc. Alternatively, oradditionally, one or more of the devices of environment 200 may performone or more functions described as being performed by another one ormore of the devices of environments 200. Devices of environment 200 mayinterconnect with each other and/or other devices via wired connections,wireless connections, or a combination of wired and wirelessconnections. In some implementations, one or more devices of environment200 may be physically integrated in, and/or may be physically attachedto, one or more other devices of environment 200.

AMF 215 may include one or more computation and communication devicesthat perform operations to register UE device 115 with the 5G network,to establish bearer channels associated with a session with UE device115, to hand off UE device 115 from the 5G network to another network,to hand off UE device 115 from the other network to the 5G network,and/or to perform other operations. In some embodiments, the 5G networkmay include multiple AMFs 215, which communicate with each other via aninterface.

SMF 220 may include one or more network devices that gather, process,store, and/or provide information in a manner described herein. SMF 220may, for example, facilitate in the establishment of communicationsessions on behalf of UE device 115. In some embodiments, theestablishment of communications sessions may be performed in accordancewith one or more policies provided by PCF 225. As described herein, SMF220 may also monitor parameters associated with traffic sent to and/orreceived from UE device 115. For instance, SMF 220 may monitor resourcesconsumed by UE device 115 (e.g., voice call minutes used, amounts ofdata sent and/or received, quantities of messages (e.g., SMS, MMS,and/or other types of messages) sent and/or received, or the like). SMF220 may perform the monitoring by, for example, communicating with UPF235 (e.g., via an interface) regarding user plane data that has beenprocessed by UPF 235. As described herein, SMF 220 may receiveinformation regarding usage and reporting rules (URRs) applied totraffic by one or more UPFs 235, in order to accurately track andcalculate the actual usage of data that is handled by UPFs 235.

PCF 225 may include one or more devices that aggregate information toand from the 5G network and/or other sources. PCF 225 may receiveinformation regarding policies and/or subscriptions from one or moresources, such as subscriber databases and/or from one or more users(such as, for example, an administrator associated with PCF 225). AF 230may include one or more devices that receive, store, and/or provideinformation that may be used in determining parameters (e.g., quality ofservice parameters, charging parameters, or the like) for certainapplications. AF 230 may maintain the information on a per-applicationbasis, in some embodiments. CHF device 245 may track resource usageassociated with UE device 115 in the telecommunications system asreported by UPF 235 for billing purposes.

UPF 235 may include one or more devices that receive, store, and/orprovide data (e.g., user plane data). For example, UPF 235 may receiveuser plane data (e.g., voice call traffic, data traffic, etc.), destinedfor UE device 115, from DN 240, and may forward the user plane datatoward UE device 115 (e.g., via RAN 105, SMF 220, and/or one or moreother devices). In some embodiments, multiple UPFs 235 may be deployed(e.g., in different geographical locations), and the delivery of contentto UE device 115 may be coordinated via an interface. Similarly, UPF 235may receive traffic from UE device 115 (e.g., via RAN 105, SMF 220,and/or one or more other devices), and may forward the traffic toward DN240. In some embodiments, UPF 235 may communicate (e.g., via an N4interface) with SMF 220, regarding user plane data processed by UPF 235.As mentioned above, this information may aid SMF 220 in monitoring(e.g., tracking, counting, etc.) the traffic for particular subscribers.As described herein, UPF 235 may, as part of a packet data unit (PDU)session setup, prepare resources and generate a PDU session resourcesetup response that includes UL tunnel information.

DN 240 may include one or more wired and/or wireless networks. Forexample, DN 240 may include an Internet Protocol (IP)-based PDN, a widearea network (WAN) such as the Internet, a private enterprise network,and/or one or more other networks. UE device 115 may communicate,through DN 240, with data servers, application servers, other UE devices115, and/or to other servers or applications that are coupled to DN 240.DN 240 may be connected to one or more other networks, such as a publicswitched telephone network (PSTN), a public land mobile network (PLMN),and/or another network. DN 240 may be connected to one or more devices,such as content providers, applications, web servers, and/or otherdevices, with which UE device 115 may communicate.

UDM 250 may include one or more devices that manage, update, and/orstore, in one or more memory devices associated with UDM 250, profileinformation associated with a subscriber. UDM 250 may performauthentication, authorization, and/or accounting operations associatedwith the subscriber and/or a communication session with UE device 115.

FIG. 3 is a diagram illustrating exemplary components of a device 300that may be included in one or more of the devices described herein. Forexample, device 300 may correspond to UE devices 115, access stations110, core devices 155, AMF 215, SMF 220, PCF 225, AF 230, UPF 235, CHF245, UDM 250, and other types of network devices or logic, as describedherein. As illustrated in FIG. 3, device 300 includes a bus 305, aprocessor 310, a memory/storage 315 that stores software 320, acommunication interface 325, an input 330, and an output 335. Accordingto other embodiments, device 300 may include fewer components,additional components, different components, and/or a differentarrangement of components than those illustrated in FIG. 3 and describedherein.

Bus 305 includes a path that permits communication among the componentsof device 300. For example, bus 305 may include a system bus, an addressbus, a data bus, and/or a control bus. Bus 305 may also include busdrivers, bus arbiters, bus interfaces, clocks, etc.

Processor 310 includes one or multiple processors, microprocessors, dataprocessors, co-processors, graphics processing units (GPUs), applicationspecific integrated circuits (ASICs), controllers, programmable logicdevices, chipsets, field-programmable gate arrays (FPGAs), applicationspecific instruction-set processors (ASIPs), system-on-chips (SoCs),central processing units (CPUs) (e.g., one or multiple cores),microcontrollers, neural processing units (NPUs), and/or some other typeof component that interprets and/or executes instructions and/or data.Processor 310 may be implemented as hardware (e.g., a microprocessor,etc.), a combination of hardware and software (e.g., an SoC, an ASIC,etc.), may include one or multiple memories (e.g., cache, etc.), etc.

Processor 310 may control the overall operation, or a portion ofoperation(s) performed by device 300. Processor 310 may perform one ormultiple operations based on an operating system and/or variousapplications or computer programs (e.g., software 320). Processor 310may access instructions from memory/storage 315, from other componentsof device 300, and/or from a source external to device 300 (e.g., anetwork, another device, etc.). Processor 310 may perform an operationand/or a process based on various techniques including, for example,multithreading, parallel processing, pipelining, interleaving, etc.

Memory/storage 315 includes one or multiple memories and/or one ormultiple other types of storage mediums. For example, memory/storage 315may include one or multiple types of memories, such as, a random accessmemory (RAM), a dynamic random access memory (DRAM), a static randomaccess memory (SRAM), a cache, a read only memory (ROM), a programmableread only memory (PROM), an erasable PROM (EPROM), an electrically EPROM(EEPROM), a single in-line memory module (SIMM), a dual in-line memorymodule (DIMM), a flash memory (e.g., 2D, 3D, NOR, NAND, etc.), a solidstate memory, and/or some other type of memory. Memory/storage 315 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid-state disk, etc.), a Micro-ElectromechanicalSystem (MEMS)-based storage medium, and/or a nanotechnology-basedstorage medium. Memory/storage 315 may include drives for reading fromand writing to the storage medium.

Memory/storage 315 may be external to and/or removable from device 300,such as, for example, a Universal Serial Bus (USB) memory stick, adongle, a hard disk, mass storage, off-line storage, or some other typeof storing medium (e.g., a compact disk (CD), a digital versatile disk(DVD), a Blu-Ray disk (BD), etc.). Memory/storage 315 may store data,software, and/or instructions related to the operation of device 300.

Software 320 includes an application or a program that provides afunction and/or a process. As an example, with reference to accessstation 110, software 320 may include an application that, when executedby processor 310, provides a function of the encoding of the tunnelingmessages system, as described herein. Additionally, for example, withreference to UE device 115, software 320 may include an applicationthat, when executed by processor 310, provides a function of theencoding of the tunneling messages system. Software 320 may also includefirmware, middleware, microcode, hardware description language (HDL),and/or other form of instruction. Software 320 may also be virtualized.Software 320 may further include an operating system (OS) (e.g.,Windows, Linux, Android, proprietary, etc.).

Communication interface 325 permits device 300 to communicate with otherdevices, networks, systems, and/or the like. Communication interface 325includes one or multiple wireless interfaces and/or wired interfaces.For example, communication interface 325 may include one or multipletransmitters and receivers, or transceivers. Communication interface 325may operate according to a protocol stack and a communication standard.Communication interface 325 may include an antenna. Communicationinterface 325 may include various processing logic or circuitry (e.g.,multiplexing/de-multiplexing, filtering, amplifying, converting, errorcorrection, application programming interface (API), etc.).Communication interface 325 may be implemented as a point-to-pointinterface, a service-based interface, etc., as previously described.

Input 330 permits an input into device 300. For example, input 330 mayinclude a keyboard, a mouse, a display, a touchscreen, a touchlessscreen, a button, a switch, an input port, speech recognition logic,and/or some other type of visual, auditory, tactile, etc., inputcomponent. Output 335 permits an output from device 300. For example,output 335 may include a speaker, a display, a touchscreen, a touchlessscreen, a light, an output port, and/or some other type of visual,auditory, tactile, etc., output component.

As previously described, a network device may be implemented accordingto various computing architectures and according to various networkarchitectures (e.g., a virtualized function, etc.). Device 300 may beimplemented in the same manner. For example, device 300 may beinstantiated, created, deleted, or some other operational state duringits life-cycle (e.g., refreshed, paused, suspended, rebooting, oranother type of state or status), using well-known virtualizationtechnologies (e.g., hypervisor, container engine, virtual container,virtual machine, etc.) in a network.

Device 300 may perform a process and/or a function, as described herein,in response to processor 310 executing software 320 stored bymemory/storage 315. By way of example, instructions may be read intomemory/storage 315 from another memory/storage 315 (not shown) or readfrom another device (not shown) via communication interface 325. Theinstructions stored by memory/storage 315 cause processor 310 to performa process and/or a function, as described herein. Alternatively, forexample, according to other implementations, device 300 performs aprocess and/or a function as described herein based on the execution ofhardware (processor 310, etc.).

FIG. 4 is a flow diagram illustrating an exemplary process 400 of anexemplary embodiment of the encoding of tunnel messaging system.According to an exemplary embodiment, wireless access station 110, SMFdevice 220, UPF device 235, and/or AMF device 215 may perform steps ofprocess 400. According to an exemplary implementation, processor 310 mayexecute software 320 to perform a step illustrated in FIG. 4 anddescribed herein. Alternatively, a step illustrated in FIG. 4 anddescribed herein, may be performed by execution of only hardware.According to an exemplary environment, process 400 may be performed in amulti-RAT RAN (e.g., a 5G-RAN and an E-UTRAN) and associated multi-corecomplementary networks, as illustrated and described herein.

FIG. 4 will be described with reference to FIG. 5, a messaging andoperations diagram illustrating an exemplary embodiment of the encodingof tunnel messaging system. Referring to FIG. 4, in block 405, a mappingtable may be generated and maintained which maps RF bandwidth categorylevels to a set of presence reporting areas (PRAs) that define acoverage area within a network. For example, SMF 220 may obtain amapping table 505 (FIG. 5) that maps a “high” RF bandwidth condition toPRA 10000001, and maps other levels of RF bandwidth conditions (e.g.,low, medium, and/or other nomenclature) to PRAs of other values.

In block 410, UE device 115 may send a PDU session establishment request510 via wireless access station 110, for example, in response to a userof UE device 115 activating/requesting an application service, which maybe routed to AMF device 215. AMF device 215 may forward the PDU sessionestablishment request 515 to SMF device 220. In block 415, SMF device220 and UPF device 235 may prepare a resources response 520 thatincludes UL tunnel information. For example, the UL tunnel info mayinclude a GTP tunnel IP (e.g., 10.1.1.11), a GTP port ID (e.g., 2152),and/or a GTP TEID (e.g., 0x00000010). In block 420, SMF device 220 maysend a PDU session resource setup request transfer information element(IE) 525 to AMF device 215, for example, using an N1 container and an N2container including the UL tunnel info. In block 425, AMF device 215 maysend an initial context setup request 530 including the N1 and N2containers to wireless station 110 (e.g., eNB).

In block 430, wireless access station 110 may generate and send aninitial context setup response 535 to AMF device 215. For example,wireless access station 110 may use DL tunnel information such as a GTPtunnel IP (e.g., 10.1.1.12), a GTP port ID (e.g., 2152), and/or GTP TEID(e.g., 0x00000001). In one implementation, the GTP TEID may includemultiple (e.g., two or more) octets of data, and wireless access station110 may configure one of the octets to include RF bandwidth supported atthe location of UE 115, as well as other types of information. Anexemplary octet with exemplary attributes, values ranges, and values isshown in Table 1 below.

TABLE 1 Attribute Value Ranges Values (# of Bits) Sector Bandwidth40-200, 201-600, 600+ MHz 0, 1, 2 (2) Highest Band Sub-3, C-Band, mmWave0, 1, 2 (2) Device Category 1-5, 6-11, 12-16, 16+ 0, 1, 2, 3 (2) DeviceRF Near, Mid, Far, Cell-edge 0, 1, 2, 3 (2)

As shown in Table 1, an exemplary octet associated with an LRE and UEdevice 115 may include bits (e.g., two least significant) that areencoded for indicating sector bandwidth information, bits (e.g., nexttwo least significant) that are encoded for indicating the highest bandsupported, bits (e.g., next two least significant) that are encoded forindicating a device category associated with UE device 110, and bits(e.g., two most significant) that are encoded for indicating the deviceRF associated with UE device 110 at the LRE. In this example, “sectorbandwidth” supported in the LRE may be categorized into three nominalvalue ranges (e.g., 40-200 MHz, 201-600 MHz, 600+ MHz), corresponding tothree extension bit values (e.g., 0, 1, 2). Other ranges are possible.The “highest band” supported in the LRE may be categorized into threenominal values (e.g., sub-3, C-band, mmWave), corresponding to threeextension bit values (e.g., 0, 1, 2). Other nominal values are possible.The “device category” for UE device 115 may be categorized into fournominal values (e.g., 1-5, 6-11, 12-16, 16+) corresponding to fourextension bit values (e.g., 0, 1, 2, 3). Other nominal values arepossible. The “device RF” for a relative position in the LRE may becategorized into four nominal values (e.g., near, mid, far, cell-edge),corresponding to four extension bit values (e.g., 0, 1, 2, 3). Othernominal values are possible.

In some embodiments, other LRE attribute information such as latencyvalues may be encoded. Additionally or alternatively, a Reference SignalReceived Power (RSRP) value, a Reference Signal Received Quality (RSRQ)value, a Received Signal Strength Indication (RSSI) value, asignal-to-interference-plus-noise ratio (SINR) value, a signal to noiseratio (SNR) value, a block error rate (BLER) value, an amplifier gainsetting value, a channel state information (CSI) report (including,e.g., Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI),Rank Indicator (RI), etc.), and/or another type of signal characteristicvalue may be encoded.

In block 435, AMF device 215 may generate and send a PDU session contextupdate 540 that includes the DL tunnel information, including theencoded GTP TEID, to SMF device 220. In block 440, SMF device 220 andUPF device 235 may update resources 545 using the encoded GTP TEID. SMFdevice 220 may analyze the encoded GTP TEID and compare the variousvalues with respect to the local bandwidth conditions, cell type, and UEdevice 115 characteristics, to corresponding values in the PRA mappingtable. Based on the comparison, SMA device 220 may generate one or morePRA reports (block 445) to send to one or more elements of core network140. For example, SMA device 220 may send one PRA report 550 to PCF 225and another PRA report 560 to CHF 245. In block 450, PCF device 225 mayuse the PRA report 550 to execute one or more corresponding policydecisions 555 (e.g., QoS policies, traffic shaping policies, etc.),and/or CHF device 245 may use the PRA report 560 to execute one or morecorresponding charging rules 565. The selected policies may be appliedto the PDU session for UE 115 accessing the network via wireless accessnetwork 110, and may be repeated, for example, when UE device 115 ishanded off to another wireless access network 110.

FIG. 4 illustrates an exemplary process 400 of the encoding of GTP TEIDsin a 5G system, however, according to other embodiments, process 400 mayinclude additional operations and/or different operations than thoseillustrated in FIG. 4 and described herein. For example, process 400 maybe performed in a 4G network and/or a multi-RAT environment, and involve4G network device, such as an eNB, an MME, an SGW/PGW, a PCRF, etc.

According to an exemplary embodiment, a RAN communicates local bandwidthconditions based on the RAN's determination of RF band combinationsinstead of the core network making interpretations of RF bandcombinations. According to an exemplary implementation, the RAN maycommunicate local RF bandwidth information at the flow or bearer levelof granularity. According to an exemplary implementation, the RAN maycommunicate local bandwidth information at the same time of sending RRCreconfiguration to the UE device or with other messages that may beexchanged during an attachment procedure and/or other procedures thatmay involve the core network (e.g., PDU session management, UE contextmanagement, UE mobility management, etc.).

As set forth in this description and illustrated by the drawings,reference is made to “an exemplary embodiment,” “an embodiment,”“embodiments,” etc., which may include a particular feature, structureor characteristic in connection with an embodiment(s). However, the useof the phrase or term “an embodiment,” “embodiments,” etc., in variousplaces in the specification does not necessarily refer to allembodiments described, nor does it necessarily refer to the sameembodiment, nor are separate or alternative embodiments necessarilymutually exclusive of other embodiment(s). The same applies to the term“implementation,” “implementations,” etc.

The foregoing description of embodiments provides illustration but isnot intended to be exhaustive or to limit the embodiments to the preciseform disclosed. Accordingly, modifications to the embodiments describedherein may be possible. For example, various modifications and changesmay be made thereto, and additional embodiments may be implemented,without departing from the broader scope of the invention as set forthin the claims that follow. The description and drawings are accordinglyto be regarded as illustrative rather than restrictive.

The terms “a,” “an,” and “the” are intended to be interpreted to includeone or more items. Further, the phrase “based on” is intended to beinterpreted as “based, at least in part, on,” unless explicitly statedotherwise. The term “and/or” is intended to be interpreted to includeany and all combinations of one or more of the associated items. Theword “exemplary” is used herein to mean “serving as an example.” Anyembodiment or implementation described as “exemplary” is not necessarilyto be construed as preferred or advantageous over other embodiments orimplementations.

In addition, while series of blocks have been described regarding theprocesses illustrated in FIGS. 4 and 5, the order of the blocks may bemodified according to other embodiments. Further, non-dependent blocksmay be performed in parallel. Additionally, other processes described inthis description may be modified and/or non-dependent operations may beperformed in parallel.

Embodiments described herein may be implemented in many different formsof software executed by hardware. For example, a process or a functionmay be implemented as “logic,” a “component,” or an “element.” Thelogic, the component, or the element, may include, for example, hardware(e.g., processor 310, etc.), or a combination of hardware and software(e.g., software 320).

Embodiments have been described without reference to the specificsoftware code because the software code can be designed to implement theembodiments based on the description herein and commercially availablesoftware design environments and/or languages. For example, varioustypes of programming languages including, for example, a compiledlanguage, an interpreted language, a declarative language, or aprocedural language may be implemented.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another, thetemporal order in which acts of a method are performed, the temporalorder in which instructions executed by a device are performed, etc.,but are used merely as labels to distinguish one claim element having acertain name from another element having a same name (but for use of theordinal term) to distinguish the claim elements.

Additionally, embodiments described herein may be implemented as anon-transitory computer-readable storage medium that stores data and/orinformation, such as instructions, program code, a data structure, aprogram module, an application, a script, or other known or conventionalform suitable for use in a computing environment. The program code,instructions, application, etc., is readable and executable by aprocessor (e.g., processor 310) of a device. A non-transitory storagemedium includes one or more of the storage mediums described in relationto memory/storage 315. The non-transitory computer-readable storagemedium may be implemented in a centralized, distributed, or logicaldivision that may include a single physical memory device or multiplephysical memory devices spread across one or multiple network devices.

To the extent the aforementioned embodiments collect, store or employpersonal information of individuals, such information shall becollected, stored, and used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Collection, storage and use ofpersonal information can be in an appropriately secure manner reflectiveof the type of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

No element, act, or instruction set forth in this description should beconstrued as critical or essential to the embodiments described hereinunless explicitly indicated as such.

All structural and functional equivalents to the elements of the variousaspects set forth in this disclosure that are known or later come to beknown are expressly incorporated herein by reference and are intended tobe encompassed by the claims.

What is claimed is:
 1. A method comprising: encoding, by a nextgeneration Node B (gNB), a general packet radio service (GPRS)-tunnelendpoint identifier (GTP-TEID) with data identifying radio frequency(RF) bandwidths supported in a local radio environment (LRE) from whicha user equipment (UE) device accesses the gNB, wherein the gNB includesa gNB-distributed unit (gNB-DU) and a gNB-centralized unit (gNB-CU);sending the encoded GTP-TEID over an interface between the gNB-DU andthe gNB-CU; sending, via a signaling channel, the encoded GTP-TEID to acore network device; notifying, by the core network device, one or morecore network devices of an RF bandwidth category level corresponding tothe identified RF bandwidths; and applying, by the one or more corenetwork devices, at least one of a policy rule or a charging rule to apacket data unit (PDU) session for the UE device, based on the RFbandwidth category level.
 2. The method of claim 1, wherein thenotifying comprises sending the RF bandwidth category level to at leastone of a policy control function (PCF) device or a charging function(CHF) device; and selecting, based on the RF bandwidth category level,the at least one of the policy rule or the charging rule.
 3. The methodof claim 1, wherein the encoded GTP-TEID comprises a plurality ofoctets, and wherein the encoding comprises configuring one or more bitsin a reserved one of the plurality of octets to identify at least one ofan RF condition of the LRE or a device category associated with the UEdevice.
 4. The method of claim 1, wherein the sending is performed at asame time that resources of the gNB are allocated for the PDU session.5. The method of claim 1, wherein the one or more core network devicescomprises a policy control function (PCF) device, and wherein the policyrule manages quality of service (QoS) for the PDU session.
 6. The methodof claim 1, the method further comprising: encoding, into the GTP-TEID,a cell type associated with the gNB; notifying the one or more corenetwork devices of the cell type; and applying the at least one of thepolicy rule or the charging rule with respect to the PDU session for theUE device, based on the cell type.
 7. The method of claim 1, wherein theinterface comprises an F1 application protocol (F1AP) interface.
 8. Adevice comprising: a plurality of processors configured to: encode ageneral packet radio service (GPRS)-tunnel endpoint identifier(GTP-TEID) with data identifying radio frequency (RF) bandwidthssupported in a local radio environment (LRE) from which a user equipment(UE) device accesses a next generation Node B (gNB) including agNB-distributed unit (gNB-DU) and a gNB-centralized unit (gNB-CU); sendthe encoded GTP-TEID over an interface between the gNB-DU and thegNB-CU; send, via a signaling channel, the encoded GTP-TEID to a corenetwork device; notify one or more core network devices of an RFbandwidth category level corresponding to the identified RF bandwidths;and apply at least one of a policy rule or a charging rule to a packetdata unit (PDU) session for the UE device, based on the RF bandwidthcategory level.
 9. The device of claim 8, wherein the notificationcomprises sending the RF bandwidth category level to at least one of apolicy control function (PCF) device or a charging function (CHF)device; and select, based on the bandwidth category level, the at leastone of the policy rule or the charging rule.
 10. The device of claim 8,wherein the encoded GTP-TEID comprises a plurality of octets, andwherein encoding comprises configuring one or more bits in a reservedone of the plurality of octets to identify at least one of an RFcondition of the LRE or a device category associated with the UE device.11. The device of claim 8, wherein the sending is performed at a sametime that resources of the gNB are allocated for the PDU session. 12.The device of claim 8, wherein the one or more other core networkdevices comprises a policy control function (PCF) device, and whereinthe policy rule manages quality of service (QoS) for the PDU session.13. The device of claim 8, wherein the processors are further configuredto: encode, into the GTP-TEID, a cell type associated with the gNB;notify the one or more core network devices of the cell type; and applythe at least one of the policy rule or the charging rule with respect tothe PDU session for the UE device, based on the cell type.
 14. Thedevice of claim 8, wherein the interface comprises an F1 applicationprotocol (F1AP) interface.
 15. A non-transitory computer-readablestorage medium storing instructions executable by a processor of adevice, which when executed cause the device to: encode a general packetradio service (GPRS)-tunnel endpoint identifier (GTP-TEID) with dataidentifying radio frequency (RF) bandwidths supported in a local radioenvironment (LRE) from which a user equipment (UE) device accesses anext generation Node B (gNB) including a gNB-distributed unit (gNB-DU)and a gNB-centralized unit (gNB-CU); send the encoded GTP-TEID over aninterface between the gNB-DU and the gNB-CU; send, via a signalingchannel, the encoded GTP-TEID to a core network device; notify one ormore core network devices of an RF bandwidth category levelcorresponding to the identified RF bandwidths; and apply at least one ofa policy rule or a charging rule to a packet data unit (PDU) session forthe UE device, based on the RF bandwidth category level.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein thenotification comprises sending the RF bandwidth category level to atleast one of a policy control function (PCF) device or a chargingfunction (CHF) device; and select, based on the RF bandwidth categorylevel, the at least one of a policy rule or a charging rule.
 17. Thenon-transitory computer-readable storage medium of claim 15, wherein theencoded GTP-TEID comprises a plurality of octets, and wherein encodingcomprises configuring one or more bits in a reserved one of theplurality of octets to identify at least one of an RF condition of theLRE or a device category associated with the UE device.
 18. Thenon-transitory computer-readable storage medium of claim 15, wherein thesending is performed at a same time that resources of the gNB areallocated for the PDU session.
 19. The non-transitory computer-readablestorage medium of claim 15, wherein the one or more other core networkdevices comprises a policy control function (PCF) device, and whereinthe policy rule manages quality of service (QoS) for the PDU session.20. The non-transitory computer-readable storage medium of claim 15,wherein the instructions further include instructions, which whenexecuted cause the device further to: encode, into the GTP-TEID, a celltype associated with the gNB; notify the one or more core networkdevices of the cell type; and apply the at least one of the policy ruleor the charging rule with respect to the PDU session for the UE device,based on the cell type; wherein the interface comprises an F1application protocol (F1AP) interface.